5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
- Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-7: Predefined Fields

PROCESS CODE


This field is used to pass information from one process to another among related and subprocess families.

  
        SET      --- PROCESS CODE           =      SUMM 
 

Query processes have special rules with respect to "sharing" of work fields and temporary work files among APPX processes. (See Interprocess Communications for more information on data sharing.) PROCESS CODE represents an exception to these special rules, as follows:

The "Setup" (Operator Interactive) phase of Query processing inherits inbound work fields and temporary files according to normal Interprocess Communication rules. But it passes outbound work fields/temp files only to the "Execution" phase of Query processing. Query (Execution) inherits inbound files/fields only from its associated Query (Setup). It can pass nothing to any subsequent job step, with the following exception:

The predefined field PROCESS CODE can be used to pass limited information into and out of Query processes. Up through Release 3.0, the application designer could not count on a Query running to completion (and making PROCESS CODE modifications available) before a subsequent Output or Update starts executing.

An exception to this is that the Query (Runtime) does not make PROCESS CODE available until after the subsequent Output/Update's Start of Process ILF series has executed, but before the first frame starts executing for the Output/Update

To access a PROCESS CODE (modified in a Query) in an Output's or Update's Start of Process, you can put a "dummy" update in after the Query, and before the subsequent Output/Update. This dummy update should be based in Query's PCF, and contain a single END PROC statement in its Start of Frame ILF series. This will make PROCESS CODE available in a subsequent Output/Update's Start of Process ILF series.

Application Design Manual                                         "Powered by Appx Software"

831

©2006 By APPX Software, Inc. All Rights Reserved